It means there was a problem communicating with server, the conection was broken. Usually this happens when the server goes offline temporarily or restarts itself. Airio then closes the connection and tries to make a new one every 5 minutes.
LFSW data cannot be received for people that expressedly blocked them in their LFS World settings. You'll see the message about not receiving LFSW data for people with blocked access or without any data.
Use 360, spinning direction does not matter. Negative numer actually allows any spin speed.
That would be because of track rotation set. When last driver leaves the server, it is like voting to end race. If defined, track rotation will be done. See RotateTracks in SRV file.
This is active by default, see the following items in SRV file:
CheckDriving=true
WrongDrivingTimeRace=5
WrongDrivingTimePrac=10
Last edited by EQ Worry, .
Open Airio.tcd.txt file, find MaximumSpin key and set it to something like 360. This sets the maximum spin in degrees per second a car can rotate in race. All faster rotating cars are spectated for security. Note that this is not a perfect crash detection, but it helps a lot on packed servers. Don't forget to use !rld after saving the updated file!
Well, possible, but then setting individual times has no meaning, bacause if you set e.g. 5, 10, 15, there'll be 15 minutes with no message between message 2 and 3. So eiher what you say, but use only one periodicity with messages rotating, or another solution:
Define pauses as e.g. 5, 15, 60, but make sure only one message is displayed, the one that was waiting the longest. That means you'll have a message displayed every 5 minutes, but on each 15th and 60th minute it will be a different message.
LOL @ the in-depth exploration. I believe you're basically right, but you should realize that you'll see message 1 and 2 at the same time at least every 7x12=84 minutes, messages 1 and 3 at least every 7x17=119 minutes and all three messages at least every 7x12x17=1428 minutes (about once in 24 hours)...
I remember I was discussing this with someone about 2 or 3 months ago. We reached a conclusion that this is not the best system and we even came up with better idea how to rotate such messages so that only one always appears. But I have no idea now what this principle was.
I remember I was discussing this with someone about 2 or 3 months ago. We reached a conclusion that this is not the best system and we even came up with better idea how to rotate such messages so that only one always appears. But I have no idea now what this principle was.
Well, I might add that size parameter, althought it is just a cosmetic change. But true, some people may prefer smaller buttons. However I consider 5 buttons (that is lines) of text maximum usable count. It has no meaning to create 10 lines of text to appear at race start, because time there is limited and you may have only 6 seconds to read it all...
TCP error means the IP/port combination you entered in CON file does not exist (is not reachable) - nothing responds there, no connection can be established. On the other hand password error means that something is responding on the set IP/port, but it does not respond correctly because you use wrong password (also in CON file) or it is some other TCP service.
Make sure the port you set in CON file is in fact server InSim port, defined by server /insim=xxxxx command, where xxxxx is often around 30000. If you can directly control your LFS server and especially if it is local (on the same computer when you run Airio), you should be always able to establish working connection. If you're using some LFS server provider, check with him the correct settings as there may be some port redirection and other strange limits...
Hi Crady! 
If fact you can even now display up to 5 big buttons with custom text on each race start (and also new connection). You can define more lines just like with other items:
RestartBtn=First button text
RestartBtn=+Second button text...
or
RestartBtn=First button text++Second button text...
Same for connect buttons, up to 5 lines/buttons may be defined...
Well, certainly possible, I'm not sure what would be the point though. There can be no valuable info in such buttons, because they are displayed only once in a lifetime.
And having "Press Shift+i" message there is rather an overkill, that instruction is always shown in chat lines anyway.
Yes, agreed, but that's how you defined it. By default there are no buttons displayed on connect or race start. If you'd like to use the buttons, I'd suggest using short server rules as connect buttons. It will not hurt people that much having to press OK after each connect, I've heard no complains yet. Race start buttons can then show good luck and some turn 1 warnings...
If fact you can even now display up to 5 big buttons with custom text on each race start (and also new connection). You can define more lines just like with other items:
RestartBtn=First button text
RestartBtn=+Second button text...
or
RestartBtn=First button text++Second button text...
Same for connect buttons, up to 5 lines/buttons may be defined...
Well, certainly possible, I'm not sure what would be the point though. There can be no valuable info in such buttons, because they are displayed only once in a lifetime.
And having "Press Shift+i" message there is rather an overkill, that instruction is always shown in chat lines anyway.Yes, agreed, but that's how you defined it.
By default there are no buttons displayed on connect or race start. If you'd like to use the buttons, I'd suggest using short server rules as connect buttons. It will not hurt people that much having to press OK after each connect, I've heard no complains yet. Race start buttons can then show good luck and some turn 1 warnings...While I'm still not personally happy about the way the championship/total things work, I think your problem has solution:
1) Open Airio.cfg.txt file.
2) Search for DaysChamp key and set it to 0 (from default value of 7). This will in effect cancel automatic champ data clearing. (Do not forget !rld to use the new setting.)
3) When you change track for the next week (which I think you're doing manually), use also !clrc admin command. This one clears all championship data for all people stored in stats.
4) The new champ data will start accumulating from this moment until you issue the !clrc command again next week (or any other time in the future).
Well, I hope this works for you and solves your troubles.
And thanks for your nice words.I'm not sure as well why the requests should be logged. But they are really requests to www.airio.eu. Maybe they're logged because they timed out? Or because some data were coming back? You can always check the !ver command output and if there are some global data it is clear the communication with www.airio.eu was successful.
Once a minute some data about your Airio instance are send as a Web request, this table is constructed from the data. Response to this info/request contains global Airio usage data (number of instances/servers and connections/drivers) that people may see in !ver command output.
The "Warning : Global stats not received..." message simply means that communication with airio.eu site was not successful, request timed out and response did not arrive within 5 seconds. There's nothing you can do about it, unfortunately my airio.eu provider has sometimes troubles, usually the situation improves in a while.
It is nothing to be worried about, just your data in the mentioned table will not be up to date or will time out (disappear) and !ver command output would also be made of old data, but that's all. As soon as the service is running again, the data will be updated.
The PubStat key is used for downloading data from LFSW and that is a very reliable service...
The "Warning : Global stats not received..." message simply means that communication with airio.eu site was not successful, request timed out and response did not arrive within 5 seconds. There's nothing you can do about it, unfortunately my airio.eu provider has sometimes troubles, usually the situation improves in a while.
It is nothing to be worried about, just your data in the mentioned table will not be up to date or will time out (disappear) and !ver command output would also be made of old data, but that's all. As soon as the service is running again, the data will be updated.
The PubStat key is used for downloading data from LFSW and that is a very reliable service...
The solution is simple: When defining the message using first !rc text command define colors exactly as you'd do it in your nickname or other text - that means press Ctrl, select color, type text. The message will be remembered including colors and e.g. !rc 10 will display it to everyone for 10 seconds, including used colors... 
If you just started your server, I'd suggest you delete all old config files, everything except EXE and PDB (and CON). Then copy into Airio directory new config files and start making configuration in those. With such major update as in your case his would be much better. You'll have all latest items available and up-to-date config files.
If you just started your server, I'd suggest you delete all old config files, everything except EXE and PDB (and CON). Then copy into Airio directory new config files and start making configuration in those. With such major update as in your case his would be much better. You'll have all latest items available and up-to-date config files.
There is in fact, and very up-to-date. But its use would require some studying of the example code, experimentation, corrections, etc. So, MSN support may be added one day, but I'm afraid that day is quite far in the future (months).
You mean notifying? He must connect himself. Some chat (and messages) can be in fact redirected/sent between connected servers, but it would be rather for fun that for some useful aim. Still, allowing textual communication between servers (e.g. via private messages) is a planned feature.
Dunno, never looked for this.
Yup, there's quite a few untranslated messages, basically all added from 1.8 to 2.2. It is only 2 days since I compiled complete new EN messages file, checked what is generally missing and sent the new messages to all the original translators. Some already responded and confirmed they'll do the translation, some are still silent.
So, updated translations are in progress. Lets wait for a few days and see if I receive new messages. Then I'll see what is missing in individual files and I hope to gradually offer language pack for 2.2. This all of course depends on people willing to sit about 30 minutes at the computer, translating silly messages.
The system tries to assess drivers' ability to drive in a clean fashion as a percentage between 100 (best driver) to 0 (worst). The rating raises a bit on every finished lap and finished race, goes down a bit with each yellow flag caused in race and bad language. These items have configurable weights. Weight of 0 means no change to the rating, positive weights raise the rating, negative lower it.
If a driver has currently rating level of 50 percent, then a rating event with weight of 100 raises the rating by 1 percent of the current rating, that is to 50.50. But the higher the rating, the less is added (making 100 percent impossible to reach). If someone has rating of 75 percent, then an event with weight of 100 raises the rating only to 75.25 while e.g. yellow flag will lower it to 74.25.
The same is true for the opposite side of the rating spectrum. Zero percent is impossible to reach and the lower your rating the less important yellow flags are and the easier it is to climb back. Overall, I think the default values function pretty well. Reasonable drivers would climb up from 50 percent to around 70. Going up from there to 80 or even 90 percent is not easy, gains accumulated over several laps and finished races may be lost by one bad accident.
And yup, I know simply counting yellow flags in races is not always just because you cause yellow flag even when the crash is not your fault. The point is it is a reliable indication over time, when people have several hundreds of rating events (shown in []). It is also possible to evade yellow flags e.g. by fast spectating/pitting when crash is inevitable, which could help keep the track clean.
Well, with IRC I use external DLL library. If such exists for MSN, it could be supported too. I guess e-mail support would be easier to add, but you'd risk being flooded with help requests several hours or days old.
Indeed admins on other connected servers managed by one instance may be reached rather easily. I'll try to think of some framework to make this possible.
I added a ButtonShowTime item into SRV file allowing to define the time. But now I think I may remove it and come with a better solution. See below:
The problem is races with low number of drivers are started rather fast. The default value of 10 seconds fits there, but it is tight. Races with 30 drivers take much longer to start, I guess it is a matter of synchronizing many LFS instances. In such cases 15 seconds could be used easily. So I even think about making the value dynamic, something between 5 and 15 seconds depending on number of cars on start. I guess that would be better than having a fixed value...
[EDIT] I did that dynamic display thing. Base value is 6 seconds, raised by one second for every 4 drivers on the start grid, reaching max. 9 seconds in demo configs and 14 seconds in S2 full grid...
Last edited by EQ Worry, .
You're welcome.
I just hope this change will not break other peoples' scripts. But as the export to ASCII is plainly wrong because strange chars are simply lost and replaced by ?, change to UFT should not be for the worse. Airio STA files are in UTF and all strange chars are internally managed (written and read) correctly.Download it again please, it has been updated a bit, the export to PB.txt is always UTF now (as you may check e.g. in Notepad). Just overwrite EXE and PDF files with the ones from newest archive, run it, try !exp, etc...
Well, updating configs directly from Airio using a super-admin rights would certainly be cool but it will also require some serious code updates. I'll see if something reasonably simple can be done.
Also such operation are always dangerous, having only one member taking care of config files has its advantages. He'll understand all the items and know the potential dangers.
In my experience after a while you'll have configs that are 95 or even more percent permanet, no changes necessary. And the few items that might need changes may be entered/prepared using !cfg or !si commands.
And it is great to always have the option to return to default functional config by !rld. If like 10 people have the power to change default config and someone does something wrong it might be pretty complicated to discover the cause of troubles, having lost previous working defaults.
Ah, yes, sorry about that. Handling LFS strings is still a nightmare. LFS Lapper file is now output as ASCII, but unfortunately this destroys all non-standard chars with code > 127. Well, the other option is to output the PB.txt file as UTF, but I'm afraid you'll hit some other troubles trying to display such characters on Web pages.
Currently I cannot offer a perfect solution. But ASCII output is simply wrong. Please try to download 2.2.4 (again if you did that just yesterday), there's UTF export implemented. See if it works better for you and let me know...
Hm, no currently this is not possible, it is always available. I plan to add admin options allowing to set some user commands availability and also default/available personal settings for (new) drivers, so hopefully I will not forget to include the !rep command there...
Yup, the Personal Info command !pi shows all information about a driver as they apply to the running instance as a whole, not depending on track/car. So in !pi you see your among other info your (or anyone else's) total laps, total points, points for playing, and rating. All these values are accompanied by your current position and total number of such items:
Most people know just about the Personal Best command !pb. That one is limited strictly to certain track/car though, showing data pertaining only to that combo:
So, in !pi you see your playing points and your current position. Based on this you can then use !ptp position command to see drivers around you in this caregory...
Overview of: мicнaeι (lokalhorst)
Raced: 20.05.2009 01:19 Laps: 4478
Points: 17304 (5/10666) | 581 (17/1103)
Ranks: Air General + 2696 = Air Marshal
Podiums: 551-63-21 (11/6674) | 23-0-0 (21/714)
Series: 117-19-14 (15/3521) | 6-0-1 (21/322)
Drifts: 117 (1278/3966)
[B]Playing: 15041 (1/6779)[/B]
Rating: 86.51% (31/3105) [298] | Pure Air (+8.49/-1.51%)
Tracks/Cars: BL2 XRG XFG (32) BL1 FBM (17272)Most people know just about the Personal Best command !pb. That one is limited strictly to certain track/car though, showing data pertaining only to that combo:
Stats for: мicнaeι (lokalhorst)
Track: BL1 Car: FBM Laps: 4451
PB: 1:12.39 Date: 27.04.2009 22:03
PB: 23.51 29.07 19.81 (0:52.58) 4/9408
TB: 1:12.15 Raced: 20.05.2009 01:19
TB: 23.47 28.92 19.76 (0:52.39) 3/9408
Licences: Air Platinum
Points: 17272 (1/6651) | 581 (12/711)
Lap time: 1:12.39 (3/6932) | 1:12.52 (3/814)
Race time: 6:08.96 (1/4850) | 6:09.04 (1/662)
Podiums: 550-63-20 (3/4075) | 23-0-0 (13/452)
Series: 117-19-14 (4/2031) | 6-0-1 (14/186)So, in !pi you see your playing points and your current position. Based on this you can then use !ptp position command to see drivers around you in this caregory...
HA! Get a new version for testing then, because Airio 2.2.4 is released with some new features as mentioned in detail in the changelog.
Airio 2.2.3 FREE dearly missed commands for showing safety ratings and total points of connected people, so I enabled these called !rate (!rt) and !rank (!rk). They are simplified versions of the same commands from the FULL version.
The above and other commands showing overview of connected people (such as !session or !time) now allow to see even drivers that do not fit withing the first 24 buttons by allowing to specify list start position. Good for heavily loaded servers. Example: !ss 20 will show best sesssion lap times from place 20, or simply last 24 people, whatever applies.
New default configuration is made so that speedtraps are installed into split points of any track. My experience shows this is much better because you can compare your speed at splits with others during race/practice. You can see your speed at every split in the rightmost button at the top of the screen when splitting data are shown. In my view this is more useful than seeing how fast was someone going using drafting or after a crash.
FULL version contains possibility to define multiple pitstops required during one race together with pit windows - specifying race minutes when a valid pit stop can be made. Drivers are informed about pit requirements at the race start and during race pitlane status changes are displayed. This is accompanied by possibility to define required actions in pits, specifically changing all tyres (useful to make pitstops more realistic) and refueling. Unfortunately repairs cannot be forced this way using available InSim info.
Also FULL version makes use of safety ratings (that seem to be working pretty good). It is possible to limit race joins by required safety rating both on server level and specific car type level. This allows to create tiered servers or tiered car types on one server (where tiered means splitting drivers by safety rating ranges). This is done by configuration items functioning exactly as those limiting race joins by rank (points) or licence (lap time).
Airio 2.2.3 FREE dearly missed commands for showing safety ratings and total points of connected people, so I enabled these called !rate (!rt) and !rank (!rk). They are simplified versions of the same commands from the FULL version.
The above and other commands showing overview of connected people (such as !session or !time) now allow to see even drivers that do not fit withing the first 24 buttons by allowing to specify list start position. Good for heavily loaded servers. Example: !ss 20 will show best sesssion lap times from place 20, or simply last 24 people, whatever applies.
New default configuration is made so that speedtraps are installed into split points of any track. My experience shows this is much better because you can compare your speed at splits with others during race/practice. You can see your speed at every split in the rightmost button at the top of the screen when splitting data are shown. In my view this is more useful than seeing how fast was someone going using drafting or after a crash.
FULL version contains possibility to define multiple pitstops required during one race together with pit windows - specifying race minutes when a valid pit stop can be made. Drivers are informed about pit requirements at the race start and during race pitlane status changes are displayed. This is accompanied by possibility to define required actions in pits, specifically changing all tyres (useful to make pitstops more realistic) and refueling. Unfortunately repairs cannot be forced this way using available InSim info.
Also FULL version makes use of safety ratings (that seem to be working pretty good). It is possible to limit race joins by required safety rating both on server level and specific car type level. This allows to create tiered servers or tiered car types on one server (where tiered means splitting drivers by safety rating ranges). This is done by configuration items functioning exactly as those limiting race joins by rank (points) or licence (lap time).
Kick/ban/spec/pen limad buttons: Good idea. A command could display all drivers, a click may select one and another click then do some forced action on that driver. I will think about it. Note that if kick/ban voting is allowed limads may have priority votes and in fact may use the voting buttons with immediate effect.
HINT: Best way to use !kick, !ban and other commands requiring names is to RIGHT-CLICK on that name in Connections list, then press HOME and type e.g. "!kk "... One click, 5 chars to type, not bad. Hm, I guess limads could as well define e.g. "!ban " as a hot key (bind). One click, two keys to use then. Better. Example: Right-click, Home, Ctrl+F1.
White list of allowed usernames/car: Uff, so many other things to improve/add, but I'll try to think about this one too. Along with some blacklist maybe.
MaximumSpin: It is a sort of crash check. Set the maximum value allowed in degrees per second. 360 seems a good value, anyone making more than one rotation a second clearly does not have the car under control. Maximum value is 720, LFS never reports higher rotation speeds.
This value supports track/car hierarchy. At the place where it is by default in TCD file there is no Track nor Car defined. That means it will apply to all tracks and all cars. Using Track and/or Car keys you may define it for individual tracks, car or combinations, as you need. Default value of -1 means this check does not run.
Knobbly tyres: Yes, these are rally tyres, but are rarely used, Hybrid are better for rallycross tracks. But Knobbly are allowed on rally tracks under default settings in TCD files. Here are the appropriate items:
The first items is set when Track and Car are empty. That means Knobbly tyres are prohibited on all tracks. But the following items specify individual rallycross tracks and change ProhibitedTyres to Normal+Super, overwriting global default.
Timed messages: Your assumption is correct. Only every change of definition updated using !rld or Airio restart sets counters so that initially all defined messages are displayed at the latest after 1 minute. This allows you to check if they are defined OK, it is a feature. Once displayed they will obey the defined intervals, still sometimes two or even three timed messages may be shown at the same time when the intervals overlap.
Rotation: Again, the described behavior is correct by design. If a track not used in rotation string is selected, there will be no rotation. I'm not sure it would be nice to force on admins rotation even if they went outside the track in rotation previously and now want to go to some other track. They would call /end and suddenly something else will load, every time. To get back into rotation one of the rotated tracks must be selected.
HINT: Best way to use !kick, !ban and other commands requiring names is to RIGHT-CLICK on that name in Connections list, then press HOME and type e.g. "!kk "... One click, 5 chars to type, not bad.
Hm, I guess limads could as well define e.g. "!ban " as a hot key (bind). One click, two keys to use then. Better. Example: Right-click, Home, Ctrl+F1.White list of allowed usernames/car: Uff, so many other things to improve/add, but I'll try to think about this one too. Along with some blacklist maybe.
MaximumSpin: It is a sort of crash check. Set the maximum value allowed in degrees per second. 360 seems a good value, anyone making more than one rotation a second clearly does not have the car under control. Maximum value is 720, LFS never reports higher rotation speeds.
This value supports track/car hierarchy. At the place where it is by default in TCD file there is no Track nor Car defined. That means it will apply to all tracks and all cars. Using Track and/or Car keys you may define it for individual tracks, car or combinations, as you need. Default value of -1 means this check does not run.
Knobbly tyres: Yes, these are rally tyres, but are rarely used, Hybrid are better for rallycross tracks. But Knobbly are allowed on rally tracks under default settings in TCD files. Here are the appropriate items:
ProhibitedTyres=Knobbly
Track=BL2
ProhibitedTyres=Normal+Super
Track=BL2R
ProhibitedTyres=Normal+Super
Track=FE5
ProhibitedTyres=Normal+Super
Track=FE5R
ProhibitedTyres=Normal+Super
Track=FE6
ProhibitedTyres=Normal+Super
Track=FE6R
ProhibitedTyres=Normal+Super
The first items is set when Track and Car are empty. That means Knobbly tyres are prohibited on all tracks. But the following items specify individual rallycross tracks and change ProhibitedTyres to Normal+Super, overwriting global default.
Timed messages: Your assumption is correct. Only every change of definition updated using !rld or Airio restart sets counters so that initially all defined messages are displayed at the latest after 1 minute. This allows you to check if they are defined OK, it is a feature.
Once displayed they will obey the defined intervals, still sometimes two or even three timed messages may be shown at the same time when the intervals overlap.Rotation: Again, the described behavior is correct by design. If a track not used in rotation string is selected, there will be no rotation. I'm not sure it would be nice to force on admins rotation even if they went outside the track in rotation previously and now want to go to some other track. They would call /end and suddenly something else will load, every time. To get back into rotation one of the rotated tracks must be selected.
Last edited by EQ Worry, .
Well, you may always create a default server/Airio setup using / and ! commands in a text file. Then you may say to youd admins: "Change whatever, but before you leave, type !si." FULL version supports automatic !si call several minutes after last driver disconnects.
Timed actions are one of the planned features. When implemented you'll be able to send any commands, including the !si x command calling some server/Airio setup. But I'm pretty sure scheduled actions will be available in FULL version only.
Hmmm, I do not see much advantages in this except he will see for how long he is yet "banned". And people may just abuse this option, connecting, shouting a while, then get kicked. And again, and again. I usually think about demo environment in these matters, and people there are really reckless. Still, if more uses for this system are found, it may be implemented, very probably reserved for FULL version only.
In FULL Airio ban (and unban) on one server is propagated to all connected servers, making admin work much easier.
Hmmm, lots of mentions of the FULL version in this my answer.
But you know, recently a guy was laughing and saying that I'm crazy offering so much in FREE version. That was after implementing custom cars, one of the most powerful Airio features, I think, and making it generally available.You can. There's a !cfg admin command available allowing to enter any item used in CFG or SRV file (not TCD file though). You may enter e.g. !cfg RotateTracks=BL1|5|FBM > BL2|5|XFG+XFX.
Confirmation is displayed and this will temporarily (in memory) change the RotateTracks item. The string used in config files will be again used after !rld or Airio restart.
Possible in two ways:
1) !cfg RotateTracks= will temporarily erase rotation string, meaning no rotation will happen. Get back to rotation by !rld.
2) Rotation happens on race end. Race end is issued only when completed races = rotate races. You may use e.g. !track 100 to set completed races on current track to 100. Very probably then completed races > rotate races and /end will never be issued.
Not possible to increase allowed chars, it is an InSim limitation, only 64 bytes may be sent. Count with additional 2 bytes on each color and language change, otherwise one char is one byte for you. Names can be up to 24 chars long.
While it would be possible to split longer messages to two lines (and on some places in Airio this happens when no part of info must be lost), it is generally not a good way to go. It should be possible to define sufficiently short messages so that they fit on one line and spamming and confusion and communication load is not increased by multiline output.
Your config looks OK, your check using !players is good.
And yes, you can kick/ban only normal drivers and limads of lower level than you have yourself. And of course no limad can kick/ban an admin, such "rank violating" commands are simply ignored...
Just read the changelog. I'm afraid I was not updating docs recently, always rather adding new things than documenting them. But the change log, if read from your current version upwards, is very good source of information.
In FREE version you may use only levels 0 (by defaul can only use team tag) and 2 (this one really has some rights). Level 1 is in FREE version switched to level 0 and level 3 to level 2. But anyway you should be able to give your limads lvl. 2 rights to kick and ban. Check the following items in Airio.cfg.txt file:
Limad2=limad_name
EnableBan=2
EnableKick=2Limads do actual kicking/banning by using Airio (not LFS) commands like !kick someone and !ban someone.
Custom commands are not yet supported, but are one of the planned features. It is only possible to define what of the existing commands may limads on different levels use.
Right, another option would be to completely disable that message, server admins may always define their own messages to be shown to each new connection. Will think about it, but it really isn't a pressing matter. As experience shows most people do not read the messages anyway, even if they are BIG BUTTONS.
LOL, understood.
Yup, using single + as line separation char was not good, because it is a very usable character. You have two options to update the text:
1) See clearly the multilines:
2) Replace single "+" for two pluses, that is "++", and have the text on just one line.
1) See clearly the multilines:
UsersMotd=^7Welcome to ^1M^7y^1D^7emo2^3 Patch Z^1!
UsersMotd=+^7Please type ^3!help ^7to see commands. ^3** ^2UPDATED! ^3**
UsersMotd=+^3PLEASE ^1read the rules ! ^7(^3Press Shift I^7)
UsersMotd=+^3We may kick/ban for breaking rules, ^1DONT DO IT!
2) Replace single "+" for two pluses, that is "++", and have the text on just one line.
Airio 2.2.3 is released, as always you'll find all changes in the change log.
Useful may be configurable support for line-separated and also tab-separated items of records in STA files. Tab-separation may be better for some post-processing, like importing into spreadsheet or reading from PHP scripts.
Major addition is a framework for driving safety ratings. It is a percentage value hinting on certain driver's abilities. The value is raised a bit by every completed lap and race, lowered by causing yellow flag and using bad language. Weights of these actions are configurable, just like overall responsiveness and start value of the system. Other rating actions may be added, ideas are welcome.
And yes, I know simply capturing yellow flags is not always right, because you cause yellow flag even if you're crashed by someone else. Still, over time it is a good indication of your abilities to evade yellow-flag situations,which are reported to you for reference.
FULL version adds the possibility to define safety rating ranges and assign them textual descriptions. Even the FREE version then supports warning and ban (for bad driving) rating levels which may help to get automatically rid of very poor drivers or crashers.
Also a new filter is added checking for equal nicknames among connected drivers, kicking the new drivers. This filter will prevent name stealing using empty characters, which LFS sees but which Airio (just like humans) ignores. Especially demo servers suffer from name stealing, when other drivers cannot simply differentiate the two people and decide if the poser is voting to ban the original or the other way.
Useful may be configurable support for line-separated and also tab-separated items of records in STA files. Tab-separation may be better for some post-processing, like importing into spreadsheet or reading from PHP scripts.
Major addition is a framework for driving safety ratings. It is a percentage value hinting on certain driver's abilities. The value is raised a bit by every completed lap and race, lowered by causing yellow flag and using bad language. Weights of these actions are configurable, just like overall responsiveness and start value of the system. Other rating actions may be added, ideas are welcome.
And yes, I know simply capturing yellow flags is not always right, because you cause yellow flag even if you're crashed by someone else. Still, over time it is a good indication of your abilities to evade yellow-flag situations,which are reported to you for reference.
FULL version adds the possibility to define safety rating ranges and assign them textual descriptions. Even the FREE version then supports warning and ban (for bad driving) rating levels which may help to get automatically rid of very poor drivers or crashers.
Also a new filter is added checking for equal nicknames among connected drivers, kicking the new drivers. This filter will prevent name stealing using empty characters, which LFS sees but which Airio (just like humans) ignores. Especially demo servers suffer from name stealing, when other drivers cannot simply differentiate the two people and decide if the poser is voting to ban the original or the other way.
FGED GREDG RDFGDR GSFDG